When starting Tails,keep the Persistent Storage locked and [[set up an administration password|doc/first_steps/welcome_screen/administration_password]].
Click on [[!img lib/network-wireless-encrypted.png alt="Unlock" class="symbolic" link="no"]]</span> to unlock the Persistent Storage. Enter the passphrase of the Persistent Storage and click **Unlock** again.
11
Identify the device name of your Persistent Storage. The device name appears below the list of volumes.It should look like <code>`/dev/mapper/luks-xxxxxxxx</code>`.
Identify the device name of your Persistent Storage. The device name appears below the list of volumes.It should look like `/dev/mapper/luks-xxxxxxxx`.
14
1. Choose <span class="menuchoice"> <span class="guimenu">Applications</span> ▸ <span class="guisubmenu">System Tools</span> ▸ <span class="guimenuitem">Root Terminal</span></span> and enter your administration password to open a root terminal.
1. Choose <span class="menuchoice"> <span class="guimenu">Applications</span> ▸ <span class="guisubmenu">System Tools</span> ▸ <span class="guimenuitem">Root Terminal</span></span> and enter your administration password to open a root terminal.
15
In the terminal, execute the following command, r. Replacing `[device]`e <span class="command-placeholder">device</span> with the device name found in step 8:
To do so, you can type <span class="command"code>fsck -y </spancode> and press <span class="keycap">**Shift+Ctrl+V</span>** to paste the device name from the clipboard.
To do so, you can type <code>fsck -y </code> and press **Shift+Ctrl+V** to paste the device name from the clipboard.
18
If the file system is free of errors, the last line from the output of <span class="command">fsck</span> starts with <span class="command">`fsck` starts with `TailsData: clean</span>`.
If the file system is free of errors, the last line from the output of `fsck` starts with `TailsData: clean`.
19
If the file system has errors, <span class="command">fsck</span>`fsck` tries to fix them automatically. After it finishes, you can try executing the same command again to check if all errors are solved.
If the file system has errors, `fsck` tries to fix them automatically. After it finishes, you can try executing the same command again to check if all errors are solved.